Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

modulesync 6.0.0 #351

Merged
merged 9 commits into from
Jun 29, 2023
Merged

modulesync 6.0.0 #351

merged 9 commits into from
Jun 29, 2023

Conversation

bastelfreak
Copy link
Member

@bastelfreak bastelfreak commented Sep 17, 2021

No description provided.

@bastelfreak bastelfreak force-pushed the modulesync branch 2 times, most recently from ca1ba76 to 91088f4 Compare July 23, 2022 08:49
@bastelfreak bastelfreak changed the title modulesync 4.2.0 modulesync 5.3.0 Jul 23, 2022
@bastelfreak
Copy link
Member Author

bastelfreak commented Jul 23, 2022

@bastelfreak bastelfreak force-pushed the modulesync branch 7 times, most recently from 325b03b to e24355f Compare July 23, 2022 09:19
Copy link
Member

@smortex smortex left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

.sync.yml Show resolved Hide resolved
@bastelfreak bastelfreak force-pushed the modulesync branch 2 times, most recently from 02ac734 to fe4ce73 Compare June 29, 2023 07:37
@bastelfreak bastelfreak force-pushed the modulesync branch 2 times, most recently from 84652c8 to 122521e Compare June 29, 2023 07:45
@bastelfreak bastelfreak changed the title modulesync 5.3.0 modulesync 6.0.0 Jun 29, 2023
@bastelfreak bastelfreak force-pushed the modulesync branch 3 times, most recently from 4e6d941 to 4404bea Compare June 29, 2023 08:15
@bastelfreak bastelfreak merged commit 20e5cec into master Jun 29, 2023
@bastelfreak bastelfreak deleted the modulesync branch June 29, 2023 08:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants